Deuteronomy: Issues and Interpretation

High Performance Transactions in Deuteronomy

The Deuteronomy architecture provides a clean separation of transaction functionality (performed in a transaction component, or TC) from data management functionality (performed in a data component, or DC). In prior work we implemented both a TC and DC that achieved modest performance. We recently built a high performance DC (the Bw-tree key value store) that achieves very high performance on m...

The All Souls Deuteronomy and the Decalogue

Focus groups: issues of analysis and interpretation.

Focus groups have become a popular method in nursing research. Their history can be traced back to marketing research methods, but they have also been used in qualitative, ethnographic research. Our study, which used this approach as part of data collection, raised many issues of analysis and interpretation: in particular, the importance of paying attention to the sequence of focus group discus...

Recursive information granulation: aggregation and interpretation issues

This paper contributes to the conceptual and algorithmic framework of information granulation. We revisit the role of information granules that are relevant to several main classes of technical pursuits involving temporal and spatial granulation. A detailed algorithm of information granulation, regarded as an optimization problem reconciling two conflicting design criteria, namely, a specificit...

Deuteronomy: Transaction Support for Cloud Data

The Deuteronomy system supports efficient and scalable ACID transactions in the cloud by decomposing functions of a database storage engine kernel into: (a) a transactional component (TC) that manages transactions and their “logical” concurrency control and undo/redo recovery, but knows nothing about physical data location and (b) a data component (DC) that maintains a data cache and uses acces...